Medical device interfacing using a camera

ABSTRACT

Methods, computer systems, and computer readable media for interfacing a medical device with an electronic medical record are provided. An image of an output of the medical device is received from a camera associated with the medical device. The image is analyzed to generate a result. The result is stored in the electronic medical record.

BACKGROUND

Many medical devices in use today are unable to interface with anelectronic medical record, or are very difficult or costly to interface.Hospitals are reluctant to spend the large amounts of money needed tobuy replacement medical devices that are able to interface with anelectronic medical record because the existing medical devices areadequate for all other purposes. Because the devices cannot interfacewith the electronic medical record, hospitals are forced to physicallystore a paper printout from the medical device, or take thelabor-intensive step of scanning the printout into the electronicmedical record.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The present invention is defined by the claims.

Embodiments of the present invention are directed to methods, computersystems, and computer storage media for use in interfacing a medicaldevice with an electronic medical record. As mentioned above, somemedical devices are unable to connect and interface with an electronicmedical record. The present invention enables these devices to interfacewith the electronic medical record by using a camera to capture an imageof an output of the medical device. The image is analyzed to generate aresult which is then stored in the electronic medical record.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitableto implement embodiments of the present invention;

FIG. 2 is a block diagram of an exemplary system environment suitablefor interfacing a medical device with an electronic medical record inaccordance with an embodiment of the present invention;

FIG. 3 depicts a flow diagram illustrating a method for interfacing amedical device with an electronic medical record suitable to implementembodiments of the present invention; and

FIG. 4 depicts a flow diagram illustrating a method for interfacing amedical device with an electronic medical record suitable to implementembodiments of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” might be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly stated.

Embodiments of the present invention are directed to methods, computersystems, and computer storage media for use in interfacing a medicaldevice with an electronic medical record (EMR). Some medical devices areunable to connect and interface with an EMR. In brief and at a highlevel, the present invention enables these devices to interface with theEMR by using a camera to capture an image of an output of the medicaldevice. The image is analyzed to generate a result which is then storedin the EMR.

Accordingly, in one embodiment, the present invention is directed towardone or more computer storage media having computer-executableinstructions embodied thereon that, when executed, facilitate a methodof interfacing a medical device with an EMR. An image of an output ofthe medical device is received from a camera associated with the medicaldevice. The image is analyzed to generate a result which is stored inthe EMR.

In another embodiment, the present invention is directed toward a systemto interface a medical device with an EMR. The system comprises a camerato record an image of an output of the medical device and one or morecomputing devices having at least one processor. The one or morecomputing devices comprise an image collector component that receivesthe image from the camera, and a determining component that determines aregion of the image to be analyzed. In addition, there is an analyzercomponent that analyzes the region and generates a result, and a storingcomponent that stores the result in the EMR.

In yet another embodiment, the present invention is directed toward oneor more computer storage media having computer-executable instructionsembodied thereon that, when executed, facilitate a method of interfacinga medical device with an EMR. An image of an output of the medicaldevice is received from a camera associated with the medical device. Aregion of the image is determined to be analyzed based upon an identityof the medical device. The region is analyzed, and a result for theregion is generated. Validation of the result for the region is receivedto provide a validated result, and the validated result is stored in theEMR.

Having briefly described embodiments of the present invention, anexemplary computing environment suitable for use in implementingembodiments of the present invention is described below. FIG. 1 is anexemplary computing environment (e.g., medical-informationcomputing-system environment) with which embodiments of the presentinvention may be implemented. The computing environment is illustratedand designated generally as reference numeral 100. The computingenvironment 100 is merely an example of one suitable computingenvironment and is not intended to suggest any limitation as to thescope of use or functionality of the invention. Neither should thecomputing environment 100 be interpreted as having any dependency orrequirement relating to any single component or combination ofcomponents illustrated therein.

The present invention might be operational with numerous other purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that might besuitable for use with the present invention include personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention might be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Exemplary program modules comprise routines,programs, objects, components, and data structures that performparticular tasks or implement particular abstract data types. Thepresent invention might be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules might be located in association with localand/or remote computer storage media (e.g., memory storage devices).

With continued reference to FIG. 1, the computing environment 100comprises a computing device in the form of a control server 102.Exemplary components of the control server 102 comprise a processingunit, internal system memory, and a suitable system bus for couplingvarious system components, including data store 104, with the controlserver 102. The system bus might be any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, and a local bus, using any of a variety of bus architectures.Exemplary architectures comprise Industry Standard Architecture (ISA)bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus,Video Electronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The control server 102 typically includes therein, or has access to, avariety of computer-readable media. Computer-readable media can be anyavailable media that might be accessed by control server 102, andincludes volatile and nonvolatile media, as well as, removable andnonremovable media. By way of example, and not limitation,computer-readable media may comprise computer storage media andcommunication media. Computer storage media includes both volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by control server 102. Communication media typicallyembodies computer-readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer-readable media.

The control server 102 might operate in a computer network 106 usinglogical connections to one or more remote computers 108. Remotecomputers 108 might be located at a variety of locations in a medical orresearch environment, including clinical laboratories (e.g., moleculardiagnostic laboratories), hospitals and other inpatient settings,veterinary environments, ambulatory settings, medical billing andfinancial offices, hospital administration settings, home healthcareenvironments, and clinicians' offices. Clinicians may comprise atreating physician or physicians; specialists such as surgeons,radiologists, cardiologists, and oncologists; emergency medicaltechnicians; physicians' assistants; nurse practitioners; nurses;nurses' aides; pharmacists; dieticians; microbiologists; laboratoryexperts; laboratory technologists; genetic counselors; researchers;veterinarians; students; and the like. The remote computers 108 mightalso be physically located in nontraditional medical care environmentsso that the entire healthcare community might be capable of integrationon the network. The remote computers 108 might be personal computers,servers, routers, network PCs, peer devices, other common network nodes,or the like and might comprise some or all of the elements describedabove in relation to the control server 102. The devices can be personaldigital assistants or other like devices.

Computer networks 106 comprise local area networks (LANs) and/or widearea networks (WANs). Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets, and the Internet.When utilized in a WAN networking environment, the control server 102might comprise a modem or other means for establishing communicationsover the WAN, such as the Internet. In a networking environment, programmodules or portions thereof might be stored in association with thecontrol server 102, the data store 104, or any of the remote computers108. For example, various application programs may reside on the memoryassociated with any one or more of the remote computers 108. It will beappreciated by those of ordinary skill in the art that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers (e.g., control server 102 andremote computers 108) might be utilized.

In operation, an organization might enter commands and information intothe control server 102 or convey the commands and information to thecontrol server 102 via one or more of the remote computers 108 throughinput devices, such as a keyboard, a pointing device (commonly referredto as a mouse), a trackball, or a touch pad. Other input devicescomprise microphones, satellite dishes, scanners, or the like. Commandsand information might also be sent directly from a remote healthcaredevice to the control server 102. In addition to a monitor, the controlserver 102 and/or remote computers 108 might comprise other peripheraloutput devices, such as speakers and a printer.

Although many other internal components of the control server 102 andthe remote computers 108 are not shown, such components and theirinterconnection are well known. Accordingly, additional detailsconcerning the internal construction of the control server 102 and theremote computers 108 are not further disclosed herein.

Turning now to FIG. 2, an exemplary system environment suitable forinterfacing a medical device with an EMR is depicted and is referencedgenerally by the numeral 200. It will be understood that the systemenvironment 200 shown in FIG. 2 is merely an example of one suitablesystem environment for use with embodiments of the present invention.Neither should the system environment 200 be interpreted as having anydependency or requirement related to any single module/component orcombination of modules/components illustrated therein. Further, many ofthe elements described herein are functional entities that may beimplemented as discrete or distributed components or in conjunction withother components/modules, and in any suitable combination and location.Various functions described herein as being performed by one or moreentities may be carried out by hardware, firmware, and/or software. Forinstance, various functions may be carried out by a processor executinginstructions stored in memory.

The system environment 200 includes a medical device interfacing system210, a camera 212, an electronic medical record (EMR) 214, an end-usercomputing device 216, and a network 218. Each of the components 210,212, 214, and 216 may be in communication with each other via thenetwork 218. The network 218 may include, without limitation, one ormore local area networks (LANs) and/or wide area networks (WANs). Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet. Accordingly, the network218 is not further described herein.

The camera 212 may comprise any camera capable of recording or capturingan image and interfacing with a computing device such as, for example,one of the remote computers 108 of FIG. 1. In one aspect, the camera 212is a Web camera capable of directly downloading images to a computer fortransmission over the network 218. In yet another aspect, the Web camerais wireless.

The camera 212 may be associated with a patient and/or a medical device.The association may occur in several different ways. For example, thecamera 212 may have software that enables the camera 212 to beassociated with a medical device which, in turn, is associated with apatient. In some embodiments, the camera 212 may be physically attachedto a medical device. Therefore, if it is known that the medical deviceis associated with a patient by, for example, associating a productidentification of the medical device with a patient identification, thenit can be assumed that the camera 212 is associated with the patientbecause it is physically attached to the medical device. Thisassociation may be strengthened by positioning the camera 212 that isattached to the medical device so that it captures or records theproduct identification of the medical device. For example, the camera212 may be positioned so that it captures a serial number of the medicaldevice, or a bar code of the medical device. The recorded productidentification of the medical device can be used as a check to verifythe camera-to-patient association.

In another embodiment, a clinician may manually associate the camera 212with a medical device and a patient by manually entering associationinformation into, for example, the medical device interfacing system210. For instance, the clinician may be interested in obtaining aone-time measurement of blood oxygen levels of a patient using a pulseoximeter. The clinician manually associates the camera 212 and the pulseoximeter device with the patient and obtains an image; the clinicianthen manually disassociates the camera 212 and the pulse oximeter devicefrom the patient. The image obtained in this manner is known to beassociated with the pulse oximeter device and the patient.

In one embodiment of the invention, the camera 212 may be positioned sothat its field of view captures the entire output of a medical device.The entire output may subsequently be analyzed to generate a series ofresults. Alternatively, selected regions of the output may be analyzedto generate results. In another embodiment, the camera 212 may bepositioned so that its field of view captures a discrete region of theimage. The region, when subsequently analyzed, may generate one result.

The EMR 214 may comprise electronic clinical documents such as images,clinical notes, summaries, reports, analyses, or other types ofelectronic medical documentation relevant to a particular patient'scondition and/or treatment. Electronic clinical documents containvarious types of information relevant to the condition and/or treatmentof a particular patient and can include information relating to, forexample, patient identification information, images, physicalexaminations, vital signs, past medical histories, surgical histories,family histories, histories of present illnesses, current and pastmedications, allergies, symptoms, past orders, completed orders, pendingorders, tasks, lab results, other test results, patient encountersand/or visits, immunizations, physician comments, nurse comments, othercaretaker comments, and a host of other relevant clinical information.The electronic clinical documents must be authenticated or signed to beconsidered a valid, legal medical record. Authenticated medical recordsstored in the EMR 214 are searchable and accessible for use in patientcare. However, the EMR 214 may also store unvalidated data and/orimages. The unvalidated data and/or images may still be used byclinicians in the decision-making process

The end-user computing device 216 may be any type of computing devicesuch as, for example, any of the remote computers 108 of FIG. 1. Theend-user computing device 216 may include a display screen (not shown).The display screen is configured to display information to the user ofthe end-user computing device 216, for instance, information relevant tocommunications initiated by and/or received by the end-user computingdevice 216, images, results, and the like. Embodiments are not intendedto be limited to visual display but rather may also include audiopresentation, combined audio/visual presentation, and the like.

The medical device interfacing system 210 shown in FIG. 2 may be anytype of computing device such as, for example, any of the remotecomputers 108 or the control server 102 of FIG. 1. By way of exampleonly and not limitation, the medical device interfacing system 210 maybe a personal computer, desktop computer, laptop computer, handhelddevice, mobile handset, consumer electronic device, server device, orthe like. It should be noted, however, that embodiments are not limitedto implementation on such computing devices, but may be implemented onany of a variety of different types of computing devices within thescope of embodiments hereof.

Components of the medical device interfacing system 210 may include,without limitation, a processing unit, internal system memory, and asuitable system bus for coupling various system components, includingone or more data stores for storing information (e.g., files andmetadata associated therewith). The medical device interfacing system210 typically includes, or has access to, a variety of computer-readablemedia.

While the medical device interfacing system 210 is illustrated as asingle unit, it will be appreciated that the medical device interfacingsystem 210 is scalable. For example, the medical device interfacingsystem 210 may in actuality include a plurality of computing devices incommunication with one another. Moreover, the EMR 214, or portionsthereof, may be included within, for instance, the medical deviceinterfacing system 210 as a computer-storage medium. The single unitdepictions are meant for clarity, not to limit the scope of embodimentsin any form.

As shown in FIG. 2, the medical device interfacing system 210 comprisesan image collector component 220, a determining component 222, ananalyzer component 224, a validation component 226, and a storingcomponent 228. In some embodiments, one or more of the components 220,222, 224, 226, and 228 may be implemented as stand-alone applications.In other embodiments, one or more of the components 220, 222, 224, 226,and 228 may be integrated directly into the operating system of, forexample, any of the remote computers 108 or the control server 102 ofFIG. 1 or the end-user computing device 216 of FIG. 2. The components220, 222, 224, 226, and 228 illustrated in FIG. 2 are exemplary innature and in number and should not be construed as limiting. Any numberof components may be employed to achieve the desired functionalitywithin the scope of embodiments hereof.

In one embodiment of the invention, the image collector component 220 isconfigured to receive an image from the camera 212, where the camera 212has recorded the image from an output of a medical device. The output ofthe medical device may be in the form of a visual display of a video ora static image, or a printout from the medical device. As well, theoutput may comprise alphanumeric characters or a wave form(s) and mayinclude the entire output of the medical device or only a portion of theoutput of the medical device. In another embodiment of the invention,the image collector component 220 may be configured to receive an imagefrom a foreign or third-party system (via some type of electronic healthinformation transmission protocol such as, for example, HL7). Forexample, wave form data may be received by the image collector component220 from a foreign system via HL7 protocol. Any and all such variationsare within the scope of embodiments of the present invention.

The image collector component 220 may, in one embodiment, be configuredto determine an identity of a medical device the camera 212 isassociated with. This can be done for example, by determining anInternet Protocol (IP) address of the camera 212. The image collectorcomponent 220 can then access a data store (for example, the data store104 of FIG. 1) to determine which medical device is associated with theIP address of the camera 212. The data store may also containinformation regarding which patient the medical device is associatedwith. By utilizing these pieces of data, a camera-to-medicaldevice-to-patient association can be established. In another embodimentof the invention, the identity of the medical device associated with thecamera 212 may already be known. For example, the camera 212 may alwaysbe associated with a certain medical device. Thus, any image receivedfrom the camera 212 will automatically be associated with that medicaldevice. In another embodiment, the identity of a medical deviceassociated with the camera 212 may already be known because a clinicianmanually associated the medical device and the camera 212 with a patientas outlined above. Still further, in yet another embodiment, when animage is received from a foreign system, the identity of the medicaldevice that generated the image may be associated with the image.

In some embodiments, the image collector component 220 may be configuredto temporarily store the image upon receiving the image and prior toanalyzing the image. Images stored in this manner may still beaccessible by clinicians for decision-making purposes. For example, theimage collector component 220 may temporarily store the image in the EMR214 or in an intermediate data store. Still further, the image may betemporarily stored based on an identity of the medical device. Theidentity of the medical device may include the type of medical device,(i.e., a vital signs monitor), the company that produced the medicaldevice, the model or serial number of the medical device, and the like.In yet another aspect, the image may be stored in a work queue that isprioritized based on the identity of the medical device. For example,images received from vital signs monitors may have a higher priority inthe work queue than images from an optical instrument used for everydayeye exams. Images may also be prioritized based on a clinical status ofa patient (stable, critical, etc.), a clinician identity, time tilldischarge, and the like.

In some embodiments of the invention, the image collector component 220may be configured to cause the camera 212 to record images. The imagecollector component 220 may cause the camera 212 to record images atfixed intervals or upon determining that an image has changed in somematerial way beyond just background noise. For example, it may bedetermined that a threshold number of pixels that comprise the imagehave changed.

The determining component 222 is configured for determining a region ofthe image to be analyzed. This determination is dependent upon theidentity of the medical device as determined by, for example, the imagecollector component 220. In one embodiment, the determining component222 may determine that the entire image, and not just a region of theimage, should be analyzed. For instance, the entire output of anelectrocardiogram (EKG) monitor contains useful information. Thedetermining component 222 determines that an entire image of the outputshould be analyzed based on the identity of the medical device—an EKGmonitor.

In another embodiment, the determining component 222 may determine thata region of the image needs to be analyzed. For example, some regions ofthe image contain data that is not particularly useful for helpingclinicians make decisions regarding patient care. But other regions ofthe image contain useful data. Again, the identity of the medical devicedetermines which regions of the image have useful data that should beanalyzed. By way of illustrative example, a spirometer measures thevolume of air inspired and expired by the lungs. The output of thespirometer may be a printout with a wave form where the peak of the waveform indicates maximum exhalation and the trough of the wave formindicates maximum inspiration. A clinician would be interested in dataregarding the peaks and troughs but not necessarily data associated withother parts of the wave form.

The analyzer component 224 is configured to analyze an image and/ordetermined region and generate results. One result may be generated ormultiple results may be generated. Images and/or regions containingalphanumeric text may be analyzed using optical character recognition(OCR) technology, while images and/or regions that consist of wave formsmay be analyzed by using waveform analysis including Fourier analysis.The results may include numerical values or text.

In one embodiment, when a medical device is always associated with thecamera 212 or when a clinician manually associates a medical device withthe camera 212, the analyzer component 224 analyzes the image andgenerates results without, for example, the image collector component220 determining an identity of the medical device. In anotherembodiment, the analyzer component 224 analyzes the image and generatesresults based on knowledge of the identity of the device as determinedby, for example, the image collector component 220. In yet anotherembodiment, the analyzer component 224 analyzes a region of the imageand generates results, where the region analyzed is determined by, forexample, the determining component 222 based on an identity of themedical device.

In one aspect of the invention, a tagging component (not shown) isconfigured to tag the image or a region of the image with a result(s).Thus, a clinician viewing the image would see tags corresponding to theresult(s). In the example given above regarding the spirometer, aclinician could access the spirometer readout image from, for example,the EMR 214 and view the image. The peaks of the image would be taggedwith a FEV1 value, and the troughs of the image would be tagged with aFIV1 value.

In yet another aspect of the invention, the validation component 226 isconfigured to present the image, and/or region, and the result(s) to auser and receive validation from the user indicating that the result(s)is valid for the image and/or region. The validation component 226 mayalso be configured to present an image with a tagged region to a userand receive validation of the tagged region from the user indicatingthat the tagged region is valid for the image. The user may be aclinician involved in the patient's care. Or the user may be an “imagetranscriptionist.” If the image does not contain sensitive patientinformation, it is possible for the transcription process to beperformed outside of patient/provider confidentiality guidelines. Oncethe clinician and/or the image transcriptionist has verified that theresult is valid for the image and/or region, or that the tagged regionis valid for the image, the image can be signed. Once the image issigned or authenticated it is considered a valid, signed medical recordthat can be accessed from the EMR 214 and used to care for the patient.

The storing component 228 is configured to store the result(s) in, forexample, the EMR 214. In one aspect, the storing component 228 isconfigured to store the result(s) and/or the image in the EMR 214. Inyet another aspect, the storing component 228 is configured to store theimage and/or any tagged regions in the EMR 214. In one embodiment, thestoring component 228 may be configured to identify a proper location inthe EMR 214 for storing the result(s). The location may be dependentupon what type of medical device generated the result(s).

The storing component 228 may store the result(s), and/or the image,and/or the tagged region in the EMR 214 before receiving validation orafter receiving validation. If it is stored before validation, aclinician or image transcriptionist would still be able to access theimage or results from the EMR 214 by using, for example, a patientidentification and use the image or results for decision-makingpurposes. The result may then be validated and re-stored in the EMR 214.If it is stored after receiving validation, it is considered a valid,signed medical record. At this point, the image can be searched andaccessed by a clinician and used to guide decisions regarding patientcare.

Turning now to FIG. 3, a high-level flow diagram is depictedillustrating a method for interfacing a medical device with anelectronic medical record and is referenced generally by the numeral300. At step 310, an image of an output of a medical device is receivedby, for example, the image collector component 220 of FIG. 2. The imagemay be received from a camera associated with the medical device. Morespecifically, the image may be received from a wireless Web cameraassociated with the medical device. The association between the cameraand the medical device may be created manually by a clinician, or theassociation may occur by physically attaching the camera to the medicaldevice and positioning it so that it captures a product identificationof the medical device. The image may be of the entire output of themedical device, or, alternatively, the image may be of a portion of theoutput of the medical device. In turn, the image may be received atfixed intervals, or the image may only be received if it is determinedthat the image has changed in some material way. In another embodimentof the invention, an image may be received from a foreign or third-partysystem.

At step 312, the image is analyzed to generate a result. In oneembodiment, the entire image is analyzed to generate one or moreresults. In another embodiment, an identity of the medical deviceassociated with the camera is determined before the image is analyzed.This may be done by, for example, the image collector component 220 ofFIG. 2. In yet another embodiment, a region of the image is determinedto be analyzed to generate one or more results by, for example, thedetermining component 222 of FIG. 2. The region to be analyzed may bedependent upon an identity of the medical device that generated theimage. At step 314, the result(s) is stored in the EMR (for example, theEMR 214 of FIG. 2) by, for example, the storing component 228 of FIG. 2.In one embodiment, the entire image along with the result is stored inthe EMR. In another embodiment, just the result is stored in the EMR.

Turning now to FIG. 4, a more detail-oriented flow diagram is depictedillustrating a method for interfacing a medical device with anelectronic medical record and is referenced generally by the numeral400. At step 410, an image of an output of a medical device is receivedfrom, for example, a camera such as the camera 212 of FIG. 2. The cameramay be a wireless Web camera. The camera may capture images at fixedintervals or upon determining that the image has changed in somematerial way. The image may be of the entire output of the medicaldevice or a portion of the output. In one embodiment, the image may betemporarily stored in a work queue upon receipt. The work queue may bestored in the EMR based upon an identity of the medical device thatproduced the image, and images in the work queue may be prioritizedbased on the identity of the medical device, a clinical status of thepatient from which the image was obtained, a clinician identity, and thelike. Images that are temporarily stored in the work queue may beavailable to clinicians for decision-making purposes.

Continuing with respect to step 410, an image may be received from aforeign or third-party system via some type of electronic healthinformation transmission protocol. Images received in this manner mayinclude information detailing an identity of a medical device thatproduced the image.

At step 412, a region of the image is determined to be analyzed basedupon an identity of the medical device. This determination may be madeby, for example, the determining component 222 of FIG. 2. As mentionedabove, the identity of the medical device may include a type of themedical device, a manufacturer of the medical device, a serial number ofthe medical device, and the like. In one embodiment, it may bedetermined that the entire image should be analyzed based on theidentity of the medical device. In another embodiment, it may bedetermined that only a region of the image contains useful informationbased on the identity of the medical device, and only that region isdetermined to be analyzed.

At step 414, the region of the image is analyzed. Optical characterrecognition may be used if the region contains alphanumeric characters,and waveform analysis may be used if the region includes wave forms. Atstep 416, a result is generated for the analyzed region. The result maybe a numerical value or text. In one embodiment, the image and/or regionis tagged with the result.

At step 418, validation of the result is received to provide a validatedresult. Validation may be received after presenting the image and/orregion and the result to a user and receiving validation from the userindicating that the result is valid for the image and/or region. Theuser may be a clinician involved in patient care, or, if privacyconcerns are maintained, the user may be an image transcriptionist thatvalidates the image outside of the normal healthcare setting. If theimage and/or region has been tagged with the result, the tagged imageand/or region may be validated.

At step 420, the validated result is stored in an EMR such as the EMR214 of FIG. 2. In one embodiment, the result may be stored in a locationthat is dependent upon the identity of the medical device that producedthe image.

The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Further, the present invention is not limitedto these embodiments, but variations and modifications may be madewithout departing from the scope of the present invention.

1. One or more computer storage media having computer-executableinstructions embodied thereon that, when executed, facilitate a methodof interfacing a medical device with an electronic medical record, themethod comprising: receiving an image of an output of the medical devicefrom a camera associated with the medical device; analyzing the image togenerate at least one result; and storing the result in the electronicmedical record.
 2. The computer storage media of claim 1, furthercomprising: causing the camera to record the image.
 3. The computerstorage media of claim 2, wherein the camera comprises a Web camera. 4.The computer storage media of claim 2, wherein the causing the camera tocapture the image occurs at fixed time intervals or upon determiningthat the image has changed in a material way.
 5. The computer storagemedia of claim 2, wherein the camera is associated with a patient. 6.The computer storage media of claim 2, wherein the output of the medicaldevice includes a visual display or a printout.
 7. The computer storagemedia of claim 2, wherein the output of the medical device comprisesalphanumeric characters or a wave form.
 8. The computer storage media ofclaim 7, wherein the alphanumeric characters are analyzed using opticalcharacter recognition and the wave form is analyzed using waveformanalysis.
 9. The computer storage media of claim 2, wherein the at leastone result comprises at least one numerical value or text.
 10. Thecomputer storage media of claim 2, further comprising: presenting theimage and the result to a user; receiving validation from the userindicating that the result is valid for the image.
 11. The computerstorage media of claim 10, wherein the user is a clinician.
 12. Thecomputer storage media of claim 2, further comprising: tagging theregion with the result.
 13. The computer storage media of claim 12,further comprising: presenting the image with the tagged region to auser; receiving validation of the tagged region from the user indicatingthat the tagged region is valid for the image; and storing the taggedregion in the electronic medical record.
 14. The computer storage mediaof claim 2, further comprising: storing the image in the electronicmedical record.
 15. A system to interface a medical device with anelectronic medical record, the system comprising: a camera to record animage of an output of the medical device; and one or more computingdevices having at least one processor and comprising: (A) an imagecollector component that receives the image from the camera, (B) adetermining component that determines a region of the image to beanalyzed, (C) an analyzer component that analyzes the region andgenerates at least one result, and (D) a storing component that storesthe at least one result in the electronic medical record.
 16. The systemof claim 15, wherein the camera is physically attached to the medicaldevice.
 17. The system of claim 16, wherein the camera is positioned torecord a product identification of the medical device.
 18. The system ofclaim 15, further comprising: a validation component that receivesvalidation of the at least one result.
 19. One or more computer storagemedia having computer-executable instructions embodied thereon that,when executed, facilitate a method of interfacing a medical device withan electronic medical record, the method comprising: receiving an imageof an output of the medical device from a camera associated with themedical device; determining a region of the image to be analyzed basedupon an identity of the medical device; analyzing the region of theimage; generating a result for the region; receiving validation of theresult for the region to provide a validated result; and storing thevalidated result in the electronic medical record.
 20. The computerstorage media of claim 19, wherein the validated result is a validmedical record.